Provide setState and setNode notifications to the drivers
#323
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
scottnc27603
force-pushed
the
development
branch
from
fd0aa1a
to
9f9d443
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Model drivers may need to know when
setStateoccurs for the application--orsetNodefor certain nodes--if the driver has private state that it can't express in its properties.When the state is refreshed in an existing client, the driver must flush this private state in order to be in sync with new clients that are joining.
kernel.setStateandkernel.setNode.setStateto all clients when new clients join.setStateon existing clients (start with http://redmine.virtualworldframework.com/issues/2182).